Apple fixed this issue after 11 days of downtime. When escalating through a DTS ticket, I eventually got a response: I can’t go into much detail about what happened here, but this was an internal data sync issue between systems that your app happened to surface, and we’ve resolved the discovered issue on our end. There isn’t any issue with your app’s code that you need to address, and pursuing this through FB21338488 was the right choice to let us investigate and address the issue for you. Can't say this is a good response, my choice will be to implement a fallback system based on OpenMeteo since I cannot trust WeatherKit to work.

Thanks for asking @darkpaw, as you can see in the original thread, it fixed itself after talking to an Apple Engineer, but it takes time. And during this time, people complain and demand refunds...

UPDATE: it started happening AGAIN... this is unacceptable for a service we pay 200$ a month for and have no transparency whatsoever.

And just like that, this morning it quietly started working again. Still haven't heard back from Apple about what happened, but filing a DTS ticket + talking to a Dev Evangelist seemed to did the trick. Still... 5 days of downtime...

I can finally prove that the requests started failing without my input: Here you can see 3 push notifications: One received on Sunday, one received Monday and another on Tuesday. The forecast for Sunday was generated correctly, but the one for Monday and Tuesday failed with the generic error message "Tap to access it". (For a little bit of more background, these are local pushes generated locally on the device using UIApplication Background Fetch) Suffice to say that I didn't touch the Developer Portal or deployed a new version to the AppStore this Sunday.

[quote='822165022, Mausa, /thread/772933?answerId=822165022#822165022, /profile/Mausa'] In the end i have used the identifier of my watch app and with that one it works.. Have no idea why this is happening, but maybe this workaround will also work for you 0  comments [/quote] Can't use this as a workaround because that means I'll have to use the REST API to make all the requests to WeatherKit, a significant lift if your coming from using the Swift API on an iOS App. I am losing my head (and quite possibly, my job) over this situation.

What's interesting is that the Widgets work... And i'm certain that the error started from Sunday to Monday, when I wasn't working...

What's interesting is that the Widgets work... And i'm certain that the error started from Sunday to Monday, when I wasn't working...

Hello! I am seeing the same thing happening on my App, which is on the AppStore and used to work perfectly up until this morning. After attaching a network debugger on my Mac, I'm seeing this 401 HTTP error: I have, of course, enabled WeatherKit on both Capabilities and App Services tabs on the Dev Portal. When running on Xcode and/or debugging via the Console, I see the same error: Failed to generate jwt token for: com.apple.weatherkit.authservice with error: Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Let me repeat: this is affecting the App that's currently deployed to the Store and has worked without hiccups before this morning. Please help because my customers are already writing!

I can confirm that switching NavigationView to NavigationStack fixes the issue for us as well. It began happening to us when updating the app using the iOS 18 SDK, and maintaining both a NavigationView and NavigationStack code branches is mental.